Date: Fri, 5 Dec 2008 00:38:21 -0800 From: "Garrett Cooper" <yanefbsd@gmail.com> To: perryh@pluto.rain.com Cc: freebsd-hackers@freebsd.org, avg@icyb.net.ua Subject: Re: ichwd problem: watchdog doesn't "bark" Message-ID: <7d6fde3d0812050038m766ecd92j352ab33bc37b6c8e@mail.gmail.com> In-Reply-To: <4938e20c.nP8q%2BJgDZ0gKUsAU%perryh@pluto.rain.com> References: <49300020.6060603@icyb.net.ua> <49382449.80002@icyb.net.ua> <4938e20c.nP8q%2BJgDZ0gKUsAU%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 5, 2008 at 12:10 AM, <perryh@pluto.rain.com> wrote: > [dropped stable@ since I'm not on it and > I suspect it may not accept non-member posts] > >> BTW, can someone knowledgeable tell me if watchdog better >> be firing SMI or NMI when it runs down? >> My bet is on NMI, but who knows. > > It may depend on whether you want the BIOS, or FreeBSD, handling > the interrupt. Unless you are running *very* old h/w, there's a > good chance the BIOS intercepts SMI, even with a protected-mode > OS running, and I wouldn't be surprised if the BIOS' response to > a watchdog timeout were an immediate reboot. It might be good > to check the motherboard and/or BIOS manuals. Yeah. I just recently have embarked on an adventure of installing FreeBSD on my work T61 laptop, and while poking around the BIOS I discovered that NMI could be enabled or disabled, so I'd determine whether or not that feature is available, and see if it's turned on or off. Intel and/or the laptop vendor should be helpful in this pursuit. -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0812050038m766ecd92j352ab33bc37b6c8e>